Using an out-of-band network to recofnigure a bus interface port

ABSTRACT

Provided are a computer program product, system, and method for using an out-of-band network to coordinate a first node reconfiguring a bus interface port used by a second node to communicate on a bus. The first node configures the bus to enable the second node to link to the bus. The second node sends a join request to the first node over an out-of-band network separate from the bus in response to determining that the second node cannot join the bus. The first node reconfigures the bus to enable the second node to communicate on the bus in response to receiving the join request from the second node over the out-of-band network.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a computer program product, system, andmethod for using an out-of-band network to coordinate reconfiguring abus interface port.

2. Description of the Related Art

In certain systems, interconnected nodes, such as servers, CentralElectronic Complexes (CEC), and other devices, may communicate and shareresources over a bus, such as a Peripheral Component InterconnectExpress (PCIe) bus. When a server attempts to connect to the bus, itchecks the link status to the bus. If the link status is notoperational, then an action is taken to repair the secondary serverconnection to the PCIe bus without affecting other devices and serversconnected to the PCIe network so they may continue to handle hostrequests to storage systems also connected to the PCIe bus.

There is a need in the art for improved techniques to reconfigure a nodeor server to connect to a bus or network if it cannot connect.

SUMMARY

Provided are a computer program product, system, and method for using anout-of-band network to coordinate a first node reconfiguring a businterface port used by a second node to communicate on a bus. The firstnode configures the bus to enable the second node to link to the bus.The second node sends a join request to the first node over anout-of-band network separate from the bus in response to determiningthat the second node cannot join the bus. The first node reconfiguresthe bus to enable the second node to communicate on the bus in responseto receiving the join request from the second node over the out-of-bandnetwork.

The described embodiments provide techniques to reconfigure the bus bysignaling a node over a separate out-of-band network to reconfigure thebus to enable a second node to communicate on the bus when the secondnode cannot connect. This allows the connection to be reset withoutintervention by an administrator or third party entity.

In further embodiments, the first node determines that the second nodeis not available and performs a failover configuration to remove thesecond node from the bus, wherein the operations of the sending the joinrequest and reconfiguring the bus are performed after second nodebecomes available after the first node performs the failoverconfiguration.

With the described embodiments, when the second node becomes availableagain after becoming unavailable and removed from the bus, the secondnode may send a join request to have the first node reconfigure the busif the second node is unable to immediately reconnect after failover.

In further embodiments, the first and second nodes communicate on thebus via first and second ports that provide first and second links tothe bus, respectively, wherein the first node during the configuring andthe reconfiguring configures the second port to be in a state that wouldallow the second node to reconnect after the second node recovers fromunavailability.

In further embodiments, the second node activates the second port tocommunicate on the bus when the second node becomes available. Thesecond node determines that a link status to connect to the bus over thesecond node is not good, and the join request is sent in response todetermining that the link status is not good.

With the described embodiments, the second node automatically pursuesout-of-band reconfiguration with the join request when determining thatthe link status after trying to reconnect after the failure is not good.

In further embodiments, the first node reconfigures hardware in the busrelated to the second port, wherein additional nodes remain connected tothe bus via additional ports while the first node reconfigures thesecond port for communication on the bus.

In further embodiments, the first node communicates to the second nodeover the out-of-band network that the reconfiguration of the second portcompleted and the second node reattempts to connect to the bus inresponse to receiving the communication over the out-of-band networkthat the reconfiguration of the second port completed.

With described embodiments, the automatic reconfiguration using theout-of-band network to signal the first node to reconfigure the bus isperformed without affecting other nodes connected on the bus because thefirst node reconfigures the bus hardware related to the second nodewithout affecting other node operations. This is particularly useful forsystems requiring continuous availability, such as embodiments where thenodes comprise servers that connect over the bus.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 illustrate embodiments of nodes linked to a bus.

FIG. 3 illustrates an embodiment of components in the nodes linked tothe bus.

FIG. 4 illustrates an embodiment of heartbeat operations for nodesconnected on the bus.

FIG. 5 illustrates an embodiment of operations for a secondary node toreconnect to the bus.

FIG. 6 illustrates an embodiment of operations to process a join requestfrom a secondary node trying to connect to the bus.

FIG. 7 illustrates an embodiment of operations performed by a secondarynode to try to reconnect to the bus after sending the join request.

FIG. 8 illustrates a computing environment in which the components ofFIG. 1 may be implemented.

DETAILED DESCRIPTION

Described embodiments provide techniques for a secondary node to notifythe controller node of the bus over an out-of-band network that the nodesecondary node cannot connect to the bus. The controller node may thenreconfigure the secondary node port and connection to the bus, and senda message to the secondary node when the reconfiguration is complete sothat the secondary node may retry to connect.

FIG. 1 illustrates an embodiment of a system having a controller node100 and one or more secondary nodes 102 ₁ . . . 102 _(n) thatcommunicate over a bus 104 with which they connect via respective busports 106 ₁, 106 ₂ . . . 106 _(n).The nodes 100, 102 ₁ . . . 102 _(n)may further include out-of-band (“OOB”) ports 108 ₁, 108 ₂ . . . 108_(n) that allow for communication over an out-of-band network 110 thatcomprises separate hardware from the bus 104. In one embodiment, the bus104 may comprise a Peripheral Component Interconnect Express (PCIe) busand the out-of-band network 110 may comprise a separate interface, suchas an Ethernet network, Storage Area Network (SAN) or a separate PCIenetwork.

In PCIe embodiments, the controller node 100 and secondary nodes 102 ₁ .. . 102 _(n) may connect over links implemented in the bus 104 thatcomprise transmit and receive pairs. The controller node 100 maycomprise a root complex processor and the other nodes 102 ₁ . . . 102_(n) may comprise endpoint devices. In further embodiments, the bus 104may comprise a PCIe switch or fabric and the nodes 100, 102 ₁ . . . 102_(n) connect to the PCIe switch 104 via a non-transparent bridge (NTB).The bus 104 forwards packets between the controller node 100 and thesecondary endpoint devices 102 ₁ . . . 102 _(n). The controller node 100may manage and maintain the bus 104 interface and send heartbeat signalsto the secondary nodes 102 ₁ . . . 102 _(n) to determine whether theyare still available and whether a failover needs to be performed toreconfigure any unavailable secondary nodes 102 ₁ . . . 102 _(n) toremove from the bus 104.

FIG. 2 illustrates an embodiment of a system 200 providing animplementation of the nodes and bus of FIG. 1. The system 200 includes acontroller server 202 and a plurality of secondary servers 204 ₁ . . .204 _(n), such as a Central Electronic Complexes (CEC), that sharenetwork adaptors 206 and storage adaptors 208. The shared networkadaptors 206 provide access to a network (not shown) to allowcommunication over the network with other hosts and the shared storageadaptors 208 provide access to shared storages 210. The servers 202, 204₁ . . . 204 _(n) and shared devices 206, 208 may operate as the nodes100, 102 ₁ . . . 102 _(n) in FIG. 1. The servers 202, 204 ₁ . . . 204_(n), shared network adaptors 206, and shared storage adaptors 208communicate over a bus 212. Further, the nodes 202, 204 ₁ . . . 204_(n), 206, 208 may also communicate through an out-of-band network 214in the manner described with respect to the nodes of FIG. 1.

FIG. 3 illustrates an embodiment of components included in a node 300,such as the nodes 100, 102 ₁ . . . 102 _(n), 202, 204 ₁ . . . 204 _(n),206, and 208 in FIGS. 1 and 2, including a connection manager 302 thatmanages connections, a bus driver 304 to communicate on the bus 104,212, an out-of-band (OOB) driver 306 to communicate on the OOB network110, 214, and node functions 308 to perform node specific operations.The components 302, 304, 306, and 308 may comprise a software program ina memory executed by a processor of the node 300. In an alternativeembodiment, some portion or all of the components 302, 304, 306, 308 maybe implemented in a hardware component, such as a dedicated integratedcircuit, e.g., Application Specific Integrated Circuit (ASIC), expansioncard, etc.

FIGS. 4-7 illustrate operations performed by the connection manager 302and bus 304 and OOB drivers 306 in the controller nodes 100, 202 and thesecondary nodes 102 ₁ . . . 102 _(n), 204 ₁ . . . 204 _(n) to handle afailover situation at one of the secondary nodes 102 _(i), 204 _(i).

FIG. 4 illustrates an embodiment of operations performed by thecontroller node 100 (or controller server 202), such as in the busdriver 304, to manage heartbeat signals to the secondary nodes 102 ₁ . .. 102 _(n), 204 ₁ . . . 204 _(n). Upon managing heartbeat signals (atblock 400), the control node 100, 202 bus driver 304 issues (at block402) heartbeat signals over the bus 104, 212 to the secondary nodes 102₁ . . . 102 _(n), 204 ₁ . . . 204 _(n). If (at block 404) one of thesecondary nodes 102 _(i), 204 _(i) has not responded to the heartbeatsignal within a time threshold, then the controller node 100, 202 busdriver 304 performs (at block 406) a failover configuration to removethe non-responding secondary node 102 _(i), 204 _(i) from the bus 104,212. The controller node 100, 202 reconfigures (at block 408) the bus104, 212 to reset the hardware settings for the port 106 _(i) on whichthe non-responding secondary node communicates to be available for thesecondary node 102 _(i) to join when available. If (at block 404) nosecondary node has not responded to the heartbeat signal for thethreshold time, then control ends. The operations of FIG. 4 may beperiodically performed by the controller node 100, 202 to periodicallydetermine whether failover needs to be performed for an unavailablesecondary node 102 _(i), 202 _(i). A secondary node 102 _(i), 202 _(i)may be unavailable as a result of a failure, error or intentional actionto take the secondary node offline for upgrades, repair, etc.

FIG. 5 illustrates an embodiment of operations performed in thesecondary node 102 _(i), 204 _(i) to connect to the bus 104, 212. Theseoperations may be performed after becoming available after beingunavailable or removed from the bus 104, 212. The operations of FIG. 5may be performed in the connection manager 302, bus driver 304, and OOBdriver 304 components of the secondary node 102 _(i), 204 _(i). Upon asecondary node 102 _(i), 204 _(i) becoming available (at block 500), thesecondary node 102 _(i), 204 _(i) connection manager 302 and bus driver304 attempts to activate (at block 502) the port 106, and link to jointhe bus. If (at block 504) the effort to join the bus 104, 112 wassuccessful, which is determined if the link status of the port 106 _(i)is good, then control ends. Otherwise, if (at block 504) the secondarynode 102 _(i), 204 _(i) bus driver 304 cannot reconnect to the bus 104,212 through the port 106 _(i), then the secondary node 102 _(i), 204_(i) connection manager 302 uses the OOB driver 304 and OOB port 108_(i) to send (at block 506) a join request to the controller node 100,202 over the out-of-band (OOB) network 110, 214 separate from the bus104, 212.

FIG. 6 illustrates an embodiment of operations performed by thecontroller node 100, 202, such as the connection manager 302, bus driver304, and OOB driver 306, upon receiving over the out-of-band network110, 214 a join request from a secondary node 102 _(i), 204 _(i) unableto reconnect to the bus 104, 212. Upon receiving (at block 600) by thecontroller node 100, 202 OOB driver 306 the join request for anidentified secondary node 102 _(i), 204 _(i) over the OOB network 104,214 on OOB port 108 ₁, the controller node 102, 202 connection manager302 may call the bus driver 304 to reconfigure (at block 602) the bus104, 212 to reset the hardware settings for the port 106 _(i) on whichthe recovering secondary node communicates. For instance, thereconfiguration operations may clear credit buffers, settings,registers, etc. for the bus port 106 _(i) used by the recoveringsecondary node 102 _(i), 204 i to communicate on the bus 104, 212. Thereconfiguration operations at block 602 may comprise the same operationsperformed at block 408 in FIG. 4.

After reconfiguring the port 106 _(i) of the recovering node 102 _(i),204 _(i), the controller node 100, 202 connection manager 302 uses theOOB driver 306 to communicate over the out-of-band network 110, 214 (atblock 604) to the secondary node 102 _(i) on OOB port 108 _(i) that sentthe join request that the reconfiguration is complete to cause thesecondary node 102 _(i), 204 _(i) to retry to connect to the bus 104,212 through the reconfigured port 106 _(i).

FIG. 7 illustrates an embodiment of operations performed by thesecondary node 102 _(i), 204 _(i) upon receiving confirmation that thereconfiguration performed in response to the join request completed.Upon receiving (at block 700) the confirmation that the reconfigurationcompleted, the secondary node 102 _(i), 204 _(i) bus driver 304 retries(at block 602) to connect to the bus 104, 212 over the bus port 106_(i). If (at block 704) the link status of the connection through thereconfigured port 106 _(i) is good, then control ends. If (at block 704)the link status is not good, then the secondary node 102 _(i), 204 _(i)connection manager 302 determines (at block 706) whether the joinrequest has been sent a maximum number of times. If so, then failure isreturned (at block 708) for the effort to connect to the bus 104, 212,which triggers some alternative troubleshooting or repair, such ascalling a repair person. If (at block 706) the request has not been sentthe maximum number of times, then the secondary node 102 _(i), 204 _(i)connection manager 302 uses the OOB driver 306 to send (at block 710) ajoin request to the controller node 100, 202 over the out-of-bandnetwork 110, 214 on OOB port 108 _(i).

With the described embodiments, a node communicating on a bus may send ajoin request over an out-of-band network if the node cannot connect overthe primary communication bus to cause the controller or primary node toreconfigure the bus port used by the node to communicate on the bus.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The computational components of FIGS. 1 and 2, including the nodes 100,102 ₁ . . . 102 _(n), 202, and 204 ₁ . . . 204 _(n) may be implementedin one or more computer systems, such as the computer system 802 shownin FIG. 8. Computer system/server 802 may be described in the generalcontext of computer system executable instructions, such as programmodules, being executed by a computer system. Generally, program modulesmay include routines, programs, objects, components, logic, datastructures, and so on that perform particular tasks or implementparticular abstract data types. Computer system/server 802 may bepracticed in distributed cloud computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed cloud computing environment,program modules may be located in both local and remote computer systemstorage media including memory storage devices.

As shown in FIG. 8, the computer system/server 802 is shown in the formof a general-purpose computing device. The components of computersystem/server 802 may include, but are not limited to, one or moreprocessors or processing units 804, a system memory 806, and a bus 808that couples various system components including system memory 806 toprocessor 804. Bus 808 represents one or more of any of several types ofbus structures, including a memory bus or memory controller, aperipheral bus, an accelerated graphics port, and a processor or localbus using any of a variety of bus architectures. By way of example, andnot limitation, such architectures include Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 802 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 802, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 806 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 810 and/or cachememory 812. Computer system/server 802 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 813 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 808 by one or more datamedia interfaces. As will be further depicted and described below,memory 806 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 814, having a set (at least one) of program modules 816,may be stored in memory 806 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. The components of the computer 802 may be implemented asprogram modules 816 which generally carry out the functions and/ormethodologies of embodiments of the invention as described herein. Thesystems of FIG. 1 may be implemented in one or more computer systems802, where if they are implemented in multiple computer systems 802,then the computer systems may communicate over a network.

Computer system/server 802 may also communicate with one or moreexternal devices 818 such as a keyboard, a pointing device, a display820, etc.; one or more devices that enable a user to interact withcomputer system/server 802; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 802 to communicate withone or more other computing devices. Such communication can occur viaInput/Output (I/O) interfaces 822. Still yet, computer system/server 802can communicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 824. As depicted, network adapter 824communicates with the other components of computer system/server 802 viabus 808. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 802. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

The reference characters used herein, such as i and n, are used hereinto denote a variable number of instances of an element, which mayrepresent the same or different values, and may represent the same ordifferent value when used with different or the same elements indifferent described instances.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims herein after appended.

What is claimed is:
 1. A computer program product for a first node andsecond node to communicate on a bus, wherein the computer programproduct comprises a computer readable storage medium having programinstructions embodied therewith, the program instructions executable byprocessors on the first and second nodes cause operations, theoperations comprising: configuring, by the first node, the bus to enablethe second node to link to the bus; sending, by the second node, a joinrequest to the first node over an out-of-band network separate from thebus in response to determining that the second node cannot join the bus;and reconfiguring the bus, by the first node, to enable the second nodeto communicate on the bus in response to receiving the join request fromthe second node over the out-of-band network.
 2. The computer programproduct of claim 1, wherein the operations further comprise: determiningby the first node that the second node is not available; and performing,by the first node, a failover configuration to remove the second nodefrom the bus, wherein the operations of the sending the join request andreconfiguring the bus are performed after second node becomes availableafter the first node performs the failover configuration.
 3. Thecomputer program product of claim 1, wherein the first and second nodescommunicate on the bus via first and second ports that provide first andsecond links to the bus, respectively, wherein the first node during theconfiguring and the reconfiguring configures the second port to be in astate that would allow the second node to reconnect after the secondnode recovers from unavailability.
 4. The computer program product ofclaim 3, wherein the operations further comprise: activating, by thesecond node, the second port to communicate on the bus when the secondnode becomes available; and determining, by the second node, that a linkstatus to connect to the bus over the second node is not good, whereinthe join request is sent in response to determining that the link statusis not good.
 5. The computer program product of claim 3, wherein thefirst node reconfigures hardware in the bus related to the second port,wherein additional nodes remain connected to the bus via additionalports while the first node reconfigures the second port forcommunication on the bus.
 6. The computer program product of claim 3,wherein the operations further comprise: communicating, by the firstnode, to the second node over the out-of-band network that thereconfiguration of the second port completed; and reattempting, by thesecond node, to connect to the bus in response to receiving thecommunication over the out-of-band network that the reconfiguration ofthe second port completed.
 7. The computer program product of claim 1,wherein the first node comprises a controller server that manages accessof secondary servers, including the second node, to the bus, whereinthere are a plurality of network and/or storage adaptors connected tothe bus, and wherein the network controller server and the secondaryservers share the network and/or storage adaptors over the bus.
 8. Thecomputer program product of claim 1, wherein the bus comprises aPeripheral Component Interconnect Express (PCIe) bus.
 9. The computerprogram product of claim 1, wherein the bus is implemented on hardwareseparate from the out-of-band network and wherein the first and secondnodes use separate third and fourth ports, respectively, to communicateon the out-of-band network.
 10. A system in communication with anout-of-band network, comprising: a bus; a first node coupled to the bus;a second node coupled to the bus; wherein the first and second nodesinclude computer programmable code that when executed by the first andsecond nodes performs operations, the operations comprising:configuring, by the first node, the bus to enable the second node tolink to the bus; sending, by the second node, a join request to thefirst node over the out-of-band network separate from the bus inresponse to determining that the second node cannot join the bus; andreconfiguring the bus, by the first node, to enable the second node tocommunicate on the bus in response to receiving the join request fromthe second node over the out-of-band network.
 11. The system of claim10, wherein the operations further comprise: determining by the firstnode that the second node is not available; and performing, by the firstnode, a failover configuration to remove the second node from the bus,wherein the operations of the sending the join request and reconfiguringthe bus are performed after second node becomes available after thefirst node performs the failover configuration.
 12. The system of claim10, wherein the first and second nodes include first and second ports,respectively, coupled to the bus that provide first and second links tothe bus, respectively, wherein the first node during the configuring andthe reconfiguring configures the second port to be in a state that wouldallow the second node to reconnect after the second node recovers fromunavailability.
 13. The system of claim 12, wherein the operationsfurther comprise: activating, by the second node, the second port tocommunicate on the bus when the second node becomes available; anddetermining, by the second node, that a link status to connect to thebus over the second node is not good, wherein the join request is sentin response to determining that the link status is not good.
 14. Thesystem of claim 12, wherein the first node reconfigures hardware in thebus related to the second port, wherein additional nodes remainconnected to the bus via additional ports while the first nodereconfigures the second port for communication on the bus.
 15. Thesystem of claim 12, wherein the operations further comprise:communicating, by the first node, to the second node over theout-of-band network that the reconfiguration of the second portcompleted; and reattempting, by the second node, to connect to the busin response to receiving the communication over the out-of-band networkthat the reconfiguration of the second port completed.
 16. The system ofclaim 10, wherein the first node comprises a controller server thatmanages access of secondary servers, including the second node, to thebus, wherein there are a plurality of network and/or storage adaptorsconnected to the bus, and wherein the network controller server and thesecondary servers share the network and/or storage adaptors over thebus.
 17. A method for configuring a first node and second node tocommunicate on a bus, comprising: configuring, by the first node, thebus to enable the second node to link to the bus; sending, by the secondnode, a join request to the first node over an out-of-band networkseparate from the bus in response to determining that the second nodecannot join the bus; and reconfiguring the bus, by the first node, toenable the second node to communicate on the bus in response toreceiving the join request from the second node over the out-of-bandnetwork.
 18. The method of claim 17, further comprising: determining bythe first node that the second node is not available; and performing, bythe first node, a failover configuration to remove the second node fromthe bus, wherein the operations of the sending the join request andreconfiguring the bus are performed after second node becomes availableafter the first node performs the failover configuration.
 19. The methodof claim 17, wherein the first and second nodes communicate on the busvia first and second ports that provide first and second links to thebus, respectively, wherein the first node during the configuring and thereconfiguring configures the second port to be in a state that wouldallow the second node to reconnect after the second node recovers fromunavailability.
 20. The method of claim 19, further comprising:activating, by the second node, the second port to communicate on thebus when the second node becomes available; and determining, by thesecond node, that a link status to connect to the bus over the secondnode is not good, wherein the join request is sent in response todetermining that the link status is not good.
 21. The method of claim19, wherein the first node reconfigures hardware in the bus related tothe second port, wherein additional nodes remain connected to the busvia additional ports while the first node reconfigures the second portfor communication on the bus.
 22. The method of claim 19, furthercomprising: communicating, by the first node, to the second node overthe out-of-band network that the reconfiguration of the second portcompleted; and reattempting, by the second node, to connect to the busin response to receiving the communication over the out-of-band networkthat the reconfiguration of the second port completed.
 23. The method ofclaim 17, wherein the first node comprises a controller server thatmanages access of secondary servers, including the second node, to thebus, wherein there are a plurality of network and/or storage adaptorsconnected to the bus, and wherein the network controller server and thesecondary servers share the network and/or storage adaptors over thebus.
 24. The method of claim 17, wherein the bus comprises a PeripheralComponent Interconnect Express (PCIe) bus.
 25. The method of claim 17,wherein the bus is implemented on hardware separate from the out-of-bandnetwork and wherein the first and second nodes use separate third andfourth ports, respectively, to communicate on the out-of-band network.